In SAS Marketing Optimization, an internal server error might occur when you create a document that has an attachment. When that happens, the following messages are generated in the SASMarketingOptimization6.3.log file:

ERROR [tomcat-http--39] ... com.sas.svcs.exceptions.MutatedException: 
(org.springframework.jdbc.UncategorizedSQLException) Error setting null for parameter #2 with
JdbcType OTHER . Try setting a different JdbcType for this parameter or a different jdbcTypeForNull 
configuration property. Cause: java.sql.SQLException: Invalid column type: 1111
   . . .more message lines. . .
Caused by: java.sql.SQLException: Invalid column type: 1111
	at oracle.jdbc.driver.OracleStatement.getInternalType(OracleStatement.java:3900)
	at oracle.jdbc.driver.OraclePreparedStatement.setNullCritical(OraclePreparedStatement.java:4406)

This problem only occurs when you use Oracle as a back-end database for the SAS^® Web Infrastructure Platform and you create documents with attachments. The problem is related to how Oracle handles the Java Database Connectivity (JDBC) Type setting for null values.

There is no workaround or circumvention for this problem.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Note:: A fix for this problem is planned for the third maintenance release of SAS^® 9.4.

Operating System and Release Information

A fix for this issue for SAS Middle Tier 9.4_M2 is available at:

A fix for this issue for SAS Middle Tier 9.4_M1 is available at: